<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<title>35. Function Port</title>
		<link type="text/css" rel="stylesheet" href="PLUGINS_ROOT/org.polarsys.capella.doc/html/styles.css"/>
	</head>
	<body>
		<h1 id="FUNCTION_PORT">FUNCTION PORT</h1>
		<h3 id="DEFINITION">DEFINITION</h3>
		<p>A Function receives inputs and delivers outputs via Function Ports. Each Input Port describes an expected input (Exchange Items), each Output Port describes an available output.</p>
		<p>A Function Port is usually identified by its name (e.g. &lsquo;tuning parameters&rsquo;, &lsquo;equalized signal&rsquo;).</p>
		<p>Function Ports can be given non functional properties characterizing the input needs or output capabilities of the Function it belongs to: e.g. specifying that a sampling function can deliver x samples per second, and compare it to a playback function needing y samples per second at input. Such non-functional properties allow securing the external use of the Function w.r.t. input and output flows: no consistency check would be possible when reusing it elsewhere in the system or from one system to another.</p>
		<h3 id="ICONS">ICONS</h3>
		<p>
			<img height="66" width="75" border="0" src="Images/35.%20Function%20Port_html_mb471f13.png"/>
			<img height="66" width="75" border="0" src="Images/35.%20Function%20Port_html_e035d14.png"/>
		</p>
		<p>
			<br/>
		</p>
	</body>
</html>